Skip to content

skim: update to 5.5.0#61569

Closed
LoricAndre wants to merge 4 commits into
void-linux:masterfrom
skim-rs:master
Closed

skim: update to 5.5.0#61569
LoricAndre wants to merge 4 commits into
void-linux:masterfrom
skim-rs:master

Conversation

@LoricAndre

Copy link
Copy Markdown

Testing the changes

  • I tested the changes in this PR: briefly (I'm running this on a non-void distro and didn't manage to run the tests, sorry)

Local build testing

  • I built this PR locally for my native architecture, (ARCH-LIBC)

@classabbyamp

Copy link
Copy Markdown
Member

packages need to be tested in Void. additionally, please read https://github.com/void-linux/.github/blob/master/CONTRIBUTING.md#ai-usage

@LoricAndre

Copy link
Copy Markdown
Author

I disabled the integration tests only, because they rely on nextest for retries and zellij for the harness. I'm not able to wire that in properly myself.
Unit and binary tests cover most of the application's surface by themselves, but I'd love to get some help to wire more in.

Sorry about the non-disclosed AI usage, this is totally on me. However, the usage was minimal : all Claude did was bump the version, nothing more, I just didn't want to waste a CI run on a later update and I was away from my computer. The rest is all me, without any AI usage at all, including choosing which tests to run.

@classabbyamp could you please treat this as my disclosure and reopen this ?

@LoricAndre LoricAndre changed the title skim: update to 5.3.2 skim: update to 5.5.0 Jul 24, 2026
@classabbyamp

Copy link
Copy Markdown
Member

why did you need to use an LLM to change a version number and run xgensum?

AI usage is not allowed regardless of disclosure

@LoricAndre

Copy link
Copy Markdown
Author

CONTRIBUTING.md says AI usage must be disclosed, nothing about it being forbidden. The changes originate from me and I understand them.

Sorry if I'm not clear. I pushed a new version of skim and didn't update this PR before shutting down my computer. When I realized I could update this PR using claude, I did it to save my time and avoid an extra CI run on void-packages' side.

@classabbyamp

Copy link
Copy Markdown
Member

All contributions are expected to be made by humans.

it's the first line of the policy

@LoricAndre

Copy link
Copy Markdown
Author

The contribution was made by me, using a tool. I don't think you'd forbid me from using my shell, text editor or any other tool that would make editing text easier for me, or consider that as the tool contributing to the project.
I can understand asking for disclosure, or blocking large changes made by unsupervised LLMs to reach the repos, but this here is a very minimal change and I don't think it warrants blocking void packages users from getting updates to their tools.

I don't use void myself, and I'm only doing this because the package looks unmaintained after no updates for nearly a year, including major versions, and I care about my work reaching users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants